gunicorn continues to be flaky so I did some more investigating of the sync server code to see if anything stands out. I realized that the log spam we see on client disconnect is because of yielding in a finally block which will run even on exit. It was better to not use finally to make sure we only yield a final message on normal exceptions, not BaseException.

That doesn't fix flakiness but just removes the log spam, in the end I realized I had tried many different low and high values for keep-alive but never tried disabling it. I think it may be more stable with it disabled, and then went back to the more lightweight worker class. We'll see how this goes, but worst case is it's still as flaky as now. Will see how it goes, and as a last resort allow failures to unblock CI in the future since we have other servers to verify with.